Apparatus and method for providing content

ABSTRACT

A method of receiving content in a client is provided. The method may include receiving, from a server, a spatial set identifier (ID) corresponding to a tile group including at least one tile, sending, to the server, a request for first content corresponding to metadata, and receiving, from the server, the first content corresponding to the request.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a Continuation application of U.S. application Ser.No. 15/488,224, filed on Apr. 14, 2017, which is a Continuationapplication of U.S. application Ser. No. 14/333,892, filed on Jul. 17,2014, which claims the benefit of Korean Patent Application No.10-2013-0085270 and of Korean Patent Application No. 10-2014-0079015,respectively filed on Jul. 19, 2013 and Jun. 26, 2014, in the KoreanIntellectual Property Office, the disclosures of which are incorporatedherein by reference.

BACKGROUND 1. Field of the Invention

The present invention relates to a technology for providing streamingcontent, and more particularly, to an apparatus and method for providingmedia content using adaptive streaming.

2. Description of the Related Art

Streaming is one of schemes for transmitting and playing back multimediacontent such as sounds, moving images, and the like. A client may playback content while receiving the content through the streaming.

An adaptive streaming service refers to providing a streaming serviceemploying a communication scheme with a request of a client and aresponse of a server corresponding to the request.

The client may request a media sequence suitable for an environment ofthe client (for example, a transmission channel of the client), usingthe adaptive streaming service. The server may provide a media sequencematched to the request of the client among media sequences with variousqualities that are included in the server.

The adaptive streaming service may be provided based on variousprotocols.

A Hypertext Transfer Protocol (HTTP) adaptive streaming service refersto an adaptive streaming service provided based on an HTTP. A client ofthe HTTP adaptive streaming service may receive content from a serverusing the HTTP, and may transmit a request associated with a streamingservice to the server.

Currently, a method of streaming a moving image while downloading themoving image using a Transmission Control Protocol (TCP) or an HTTP iswidely used. In a Moving Picture Experts Group (MPEG), that is, astandardization group that sets standards for moving images, a method ofstreaming a moving image while downloading the moving image using anHTTP through a project called “Dynamic Adaptive Streaming over HTTP(DASH)” has been standardized. An existing TCP- or HTTP-based movingimage transmission method, and a method of classifying a single programinto segments divided in a unit of time, sequentially downloading thesegments and playing back the program in an MPEG-DASH are used. In theabove process, an appropriate bandwidth or a type of moving images maybe selected based on an environment of a terminal or a network.

SUMMARY

According to an aspect of the present invention, there is provided amethod of receiving content in a client, including: receiving, from aserver, a spatial set identifier (ID) for a group of at least onespatial object; sending, to the server, a request for first contentcorresponding to the spatial set ID; and receiving, from the server, thefirst content corresponding to the request.

The spatial set ID may be used to identify a tile group including atleast one of tiles into which full-frame video is spatially divided.

The first content may be video corresponding to the tile group.

The spatial set ID may be used to group sets of the at least one spatialobject.

The receiving of the spatial set ID may include receiving metadataincluding the spatial set ID.

The metadata may be a Media Presentation Description (MPD) of content.

The MPD may include a Spatial Relationship Description (SRD).

The SRD may include at least one of the spatial set ID, and an x-axisposition, a y-axis position, a width, a height, a reference spatialwidth, and a reference spatial height of the spatial object.

The sending of the request may include transmitting, to the server, arequest including a Uniform Resource Locator (URL) corresponding to thefirst content.

The URL may include a URL corresponding to one of tiles into whichfull-frame video is spatially divided.

According to another aspect of the present invention, there is provideda method of transmitting content in a server, including: transmitting,to a client, a spatial set ID for a group of at least one spatialobject; receiving, from the client, a request for first contentcorresponding to the spatial set ID; and transmitting, to the client,the first content corresponding to the request.

The spatial set ID may include at least one of tiles into whichfull-frame video is spatially divided.

The first content may be video corresponding to a tile group.

The spatial set ID may be used to group sets of the at least one spatialobject.

The transmitting of the spatial set ID may include transmitting metadataincluding at least one of the spatial set ID, and an x-axis position, ay-axis position, a width, a height, a reference spatial width, and areference spatial height of the spatial object.

The metadata may be an MPD of content.

The MPD may include an SRD.

The SRD may include the spatial set ID.

The receiving of the request may include receiving, from the client, arequest including a URL corresponding to the first content.

The URL may include a URL corresponding to one of tiles into whichfull-frame video is spatially divided.

According to various embodiments, a method and apparatus fortransmitting spatially divided moving image content in a unit of aspatial segment may be provided.

When streaming is performed using spatial segments into which singlecontent is divided, a position of each of the spatial segments may besimply displayed, and a subset of spatial segments and separate indexinformation may be provided.

BRIEF DESCRIPTION OF THE DRAWINGS

These and/or other aspects, features, and advantages of the inventionwill become apparent and more readily appreciated from the followingdescription of exemplary embodiments, taken in conjunction with theaccompanying drawings of which:

FIGS. 1A and 1B are diagrams illustrating spatially divided moving imagecontent according to an embodiment;

FIG. 2 is a flowchart illustrating a signal processing process accordingto an embodiment;

FIG. 3 is a diagram illustrating an example of a hierarchy of a spatialsegment according to an embodiment;

FIG. 4 is a diagram illustrating another example of a hierarchy of aspatial segment according to an embodiment;

FIG. 5 is a block diagram illustrating an example of a configuration ofa client according to an embodiment; and

FIG. 6 is a diagram illustrating another example of a configuration of aclient according to an embodiment.

DETAILED DESCRIPTION

Reference will now be made in detail to exemplary embodiments of thepresent invention, examples of which are illustrated in the accompanyingdrawings, wherein like reference numerals refer to the like elementsthroughout. Exemplary embodiments are described below to explain thepresent invention by referring to the figures.

A Dynamic Adaptive Streaming over Hypertext Transfer Protocol (HTTP)(DASH) may specify formats that enable 1) transferring of media contentfrom an HTTP server to an HTTP client, and 2) caching of content bystandard HTTP caches.

A media component may be an encoded version of individual media types,such as audios, videos, or timed texts that have specific attributes,for example bandwidths, languages, or resolutions.

Media content may be a set of media components having a common timeline,for example audios, videos, or timed texts. Additionally, mediacomponents may have relationships on how the media components may bepresented (for example, individually, jointly, or mutually exclusive) asprograms or movies.

The terms “media content” and “content” may be interchangeably used withrespect to each other.

A media presentation may be a structured collection of data used toestablish bounded or unbounded presentation of media content includingconsecutive media components.

In other words, the media presentation may be a structured collection ofdata enabling access to a DASH client in order to provide a streamingservice to a user.

A Media Presentation Description (MPD) may be a formalized descriptionof a media presentation.

The media presentation may include possible updates of the MPD, and maybe described by the MPD.

Content may be content on demand, or live content.

The content may be divided into one or more intervals. In other words,the content may include one or more intervals.

The terms “interval” and “period” may be interchangeably used withrespect to each other. The term “period” may be used as a term of 3^(rd)Generation Partnership Project (3GPP) adaptive HTTP streaming.

A period may be an interval of a media presentation. Consecutivesequences of all periods may form a media presentation.

In other words, the media presentation may include one or more periods.

One or more intervals may be a basic unit. One or more intervals may bedescribed by signaling metadata. In other words, metadata may describeeach of the one or more intervals.

The metadata may be an MPD.

The MPD may define a format to inform of resource identifiers (IDs) forsegments. The MPD may provide a context regarding resources identifiedin the media presentation. The resource IDs may be HTTP-Uniform ResourceLocators (URLs). URLs may be restricted by a byte range attribute.

Each interval may be divided into fragments.

The terms “fragment” and “segment” may be interchangeably used withrespect to each other. The term “segment” may be used as a term of 3GPPadaptive HTTP streaming.

A segment may refer to an entity body of a response to an HTTP/1.1 GETrequest for an HTTP-URL, for example as defined in RFC 2616, (or a GETrequest for a part indicated by a byte range). The metadata may includea URL attribute, and a range attribute. A client may receive bytesdesignated by the range attribute from a URL indicated by the URLattribute. In other words, the bytes may be received by a partial HTTPGET command for the URL instructed by the byte range. The bytesdesignated by the range attribute may represent the above-describedsegment.

The range attribute may indicate multiple byte ranges.

The client may play back media content using the received bytes, thatis, segments.

A sub-segment may refer to a smallest unit in segments that may beindexed by a segment index in a segment level.

Two or more sets of fragments corresponding to a single interval mayexist. Each of the sets may be called an alternative.

The terms “alternative” and “representation (or an expression)” and“expression” may be interchangeably used with respect to each other.

Each period may include one or more groups.

Each group may include one or more representations of the same mediacontent.

The representation may refer to a structured collection of one or moremedia components in a single period.

An MPD (or an MPD element) may provide descriptive information thatenables a client to select one or more representations.

A Random Access Point (RAP) may be a specific location in a mediasegment. The RAP may be identified as a location in which playback maybe started continuously from a location of the RAP based on onlyinformation included in a media segment.

Each representation may be formed of one or more segments. In otherwords, a representation may include one or more segments.

An MPD may be a document including metadata required to a DASH client toform appropriate HTTP-URLs in order to 1) access segments and to 2)provide a user with a streaming service. The HTTP-URLs may be absoluteor relative.

The MPD may be an Extensible Markup Language (XML)-document.

The MPD may include an MPD element. The MPD may include only a singleMPD element.

A client may be a DASH client.

The DASH client may be compatible with a client specified in RFC 2616.

The DASH client may typically use an HTTP GET method or an HTTP partialGET method, as specified in RFC 2616, to access segments or parts ofsegments.

FIGS. 1A and 1B are diagrams illustrating spatially divided moving imagecontent according to an embodiment.

As shown in FIGS. 1A and 1B, single content may be spatially dividedinto 24 segments. In the following description, segments may be referredto as “tiles” or “pieces.” A segment ID may be assigned to each ofsegments.

A spatial relationship may be defined. The spatial relationship may beassociated with video representing a spatial part of full-frame video.The spatial part may be an interest region or a tile that is describedwith terms “position” and “size.” The above description may be expressedwith a term “adaptation,” and may provide additional selection for aclient.

Additionally, a spatial relationship description (SRD) may be defined.The SRD may allow media presentation authors to express spatialrelationships between spatial objects. A spatial object may berepresented by either an adaptation set or a sub-presentation. Thespatial relationship may express video representing a spatial part offull-frame video. In FIGS. 1A and 1B, video representing a spatial partof full-frame video, or a group of video representing a spatial part maybe referred to as a “spatial object.” To preserve compatibility withlegacy clients, MPD authors may use SupplementalProperty andEssentialProperty so that at least one Representation may be interpretedby legacy clients after discarding an element includingEssentialProperty.

A DASH client may recognize an SRD, and may select a full-framerepresentation or a spatial part of the full-frame representation usingan SRD annotation to meet requirements. Accordingly, a bandwidth andcomputation of a client may be reduced, which may be caused bypreventing full-frame fetching, decoding and cropping.

In an embodiment, when a size occupied by each spatial segment isidentical, a number of columns of a spatial segment, a number of rows ofa spatial segment, and a scheme of arranging spatial segments may bedescribed, and an ID enabling verification of a simple numeral or ordermay be described in a spatial segment description unit.

For example, 24 spatial segments of FIGS. 1A and 1B may be arrangedusing a horizontal raster scan scheme or a vertical raster scan scheme.In this example, information regarding a number of columns of a spatialsegment, a number of rows of a spatial segment, and a direction in whichspatial segments are arranged may be actually transferred.

For example, coordinates (x, y) of a top left vertex of a tile with atile ID of 19 of FIG. 1A, a width w and a height h of the tile, and awidth W and a height H of full-frame video may be included in an SRD,and may be referred to as “SRD parameters.” Additionally, the SRD mayinclude an ID of a source including a tile or full-frame video.

A parameter source_id may provide a unique ID for a source of content,within a Period. The parameter source_id may implicitly define acoordinate system associated with the source. The coordinate system mayinclude an arbitrary origin (0; 0), an x-axis may be oriented from leftto right, and a y-axis may be oriented from top to bottom. All SRDsharing the same value of the parameter source_id may have the sameorigin and axes orientations. Spatial relationships for spatial objectsusing an SRD with different values of the parameter source_id may not bedefined.

Additionally, parameters x and y may express two-dimensional (2D)positions of a related spatial object in the coordinate systemassociated with the source. Parameters w and h may express 2D sizes ofthe related spatial object in the coordinate system associated with thesource. Values of the parameters x, y, w, and h may be relative tovalues of parameters W and H. Positions (x, y) and sizes (w, h) of SRDsharing the same value of the parameter source_id may be compared aftertaking into account a size of a reference space, i.e., after the valuesof the parameters x and w are divided by the value of the parameter Wand the values of the parameters y and h are divided by the value of theparameter H.

Different values of W and H may be used in different descriptors toprovide position and size information in different units.

A group ID may be defined. The group ID may be an ID indicating a groupincluding tiles included in a basic view based on a user's request or atbeginning of playback of content, and will be further described below.The group ID may be referred to as “spatial_set_id.” In the presentdescription, the spatial_set_id may be interchangeably used with respectto the group ID, however, may also be defined as an ID for a group ofspatial objects.

FIG. 2 is a flowchart illustrating a signal processing process accordingto an embodiment.

As shown in FIG. 2, a client 100 and a server 110 may communicate witheach other. The client 100 may be a DASH client. The DASH client may becompatible with a client specified in RFC 2616.

The DASH client may typically use an HTTP GET method or an HTTP partialGET method, as specified in RFC 2616, to access segments or parts ofsegments.

The server 110 may perform hosting on DASH segments. The server 110 maybe compatible with a server specified in RFC 2616.

In operation 120, the client 100 may receive, from the server 110, 1)metadata of content, or 2) metadata of a specific interval of thecontent. In other words, the server 110 may transmit, to the client100, 1) the metadata of the content, or 2) the metadata of the specificinterval of the content. The specific interval may indicate a currentlyprocessed interval among one or more intervals forming the content.

The metadata may be an MPD of media content. Additionally, the MPD mayinclude an SRD, and the SRD may include at least one of a group ID and atile ID. The group ID may be an ID indicating a group including tilesincluded in a basic view based on a user's request or at beginning ofplayback of content. In other words, the group ID may be an ID used togroup sets of spatial representations. For example, in an SRD as shownin FIG. 1A, a tile group with a group ID of “0” may be set to includetiles with tile IDs of 15, 16, 21, and 22. Additionally, a tile groupwith a group ID of “1” may be set to include tiles with tile IDs of 11,12, 17, and 18. The group ID may be set to “0” or a natural number.

Content represented by either an adaptation set or a sub-representationmay be defined as a spatial object. The group ID may also be defined asan ID for a group of spatial objects.

For example, in operation 120, the client 100 may receive metadataincluding the group ID of “1” from the server 110.

In operation 130, the client 100 may process the metadata of thespecific interval. For example, the client 100 may verify the group ID,and may verify content to be received.

In operation 140, the client 100 may send a request for content or afragment to the server 110. The client 100 may request the server 110 totransmit content suitable for the specific interval based on theprocessed metadata. In other words, the requested content may beselected based on the metadata. For example, the client 100 may requestfor content including a tile group corresponding to the group ID. In anembodiment, the client 100 may transmit, to the server 110, a requestincluding a URL corresponding to a tile group. The request may include aplurality of URLs. For example, the client 100 may transmit, to theserver 110, a request including a URL corresponding to each of tileswith tile IDs of 11, 12, 17, and 18.

In operation 150, the server 110 may transmit, to the client 100,content suitable for each request from the client 100. The client 100may receive the content from the server 110. For example, the client 100may receive tiles with tile IDs of 11, 12, 17, and 18, that is, receivea tile group.

The overall process may be performed again. For example, operation 120may be repeatedly performed on an interval next to the specificinterval.

The client 100 may play back content using fragments received byrepeating operations 120 to 150.

As described above, the client 100 may receive content including partialtiles, instead of receiving full-frame video. Accordingly, a bandwidthand a computation amount may be significantly reduced.

The above-described embodiment is merely an example and accordingly, maybe equally applied to a tile ID, instead of a group ID. For example, theclient 100 may receive metadata including a tile ID. The client 100 maytransmit a request including a URL corresponding to the tile ID to theserver 110. The server 110 may transmit corresponding content to theclient 100.

Hereinafter, a hierarchy of a spatial segment according to variousembodiments will be described.

FIG. 3 is a diagram illustrating an example of a hierarchy of a spatialsegment according to an embodiment.

As shown in FIG. 3, to display a spatial segment in an element Period ofan MPD defined in a DASH, a number of columns of a spatial segment, anumber of rows of a spatial segment, and a scheme of arranging spatialsegments may be described, and an ID enabling verification of a simplenumeral or order may be described in each spatial segment descriptionunit, that is, an element AdaptationSet. In the following description,numOfColumns may indicate a number of columns of a spatial segment, thatis, a tile, numOfRows may indicate a number of rows of a tile, andtypeOfNumbering may indicate a scheme of arranging tiles. ThenumOfColumns, numOfRows, and typeOfNumbering may be added to the elementPeriod and a tileId may be added to each adaptation set, which mayenable recognition of a spatial position of a tile. Referring to FIG. 3,numOfColumns set to “6,” numOfRows set to “4” and typeOfNumbering set toa horizontal raster scan scheme may be described. Semantics and XMLsyntax of the element Period may be represented as follows:

numOfColumns : number of tile columns numOfRows : number of tile rowstypeOfNumbering : numbering or scanning type of tiles tileId :Sequential number to indicate a tile and its position <xs:complexTypename=“PeriodType”> <xs:sequence><xs:element name=“BaseURL” type=“BaseURLType” minOccurs=“0”maxOccurs=“unbounded”/> <xs:element name=“SegmentBase”type=“SegmentBaseType” minOccurs=“0”/> <xs:element name=“SegmentList”type=“SegmentListType” minOccurs=“0”/><xs:element name=“SegmentTemplate” type=“SegmentTemplateType”minOccurs=“0”/> <xs:element name=“AdaptationSet”type=“AdaptationSetType” minOccurs=“0” maxOccurs=“unbounded”/><xs:element name=“Subset” type=“SubsetType” minOccurs=“0”maxOccurs=“unbounded”/><xs:any namespace=“##other” processContents=“lax” minOccurs=“0”maxOccurs=“unbounded”/> </xs:sequence> <xs:attribute ref=“xlink:href”/><xs:attribute ref=“xlink:actuate” default=“onRequest”/> <xs:attributename=“id” type=“xs:string” /> <xs:attribute name=“start”type=“xs:duration”/> <xs:attribute name=“duration” type=“xs:duration”/><xs:attribute name=“bitstreamSwitching” type=“xs:boolean”default=“false”/> <xs:attribute name=“numOfColumns”type=“xs:unsignedInt” use=“optional” /> <xs:attribute name=“numOfRows”type=“xs:unsignedInt” use=“optional” /> <xs:attributename=“typeOfNumbering” type=“xs:string” use=“optional” /> <xs:anyAttribute namespace=“##other” processContents=“lax”/> </xs:complexType>

In another embodiment, a method of representing a subset of spatialsegments while individually describing and transferring information on aplurality of spatial segments, that is, tiles may enable variableapplications. For example, to specify a spatial region as a center of ascreen, a spatial segment subset may be separately provided, or a regionin which an important event, for example a decisive scene in sports,occurs may be displayed. Additionally, a region as a basic view in wholespace may be displayed through a spatial segment subset. To this end,subset information including a plurality of IDs of spatial segments maybe separately provided, and may be a group ID.

In an example, in a DASH, a subset of tiles described as an SRD in aPeriod of an MPD may be displayed using a tile included in a basic viewbased on a user's request or at beginning of playback of content througha new element DefaultView.

Alternatively, a separate element, for example, TileGroup that is asubset of tiles may be added to the Period and accordingly, spatialsegment IDs may be arranged, or SubSet among elements included incurrent MPD::Period may be extended. For example, ExtendedSubSet may bedefined by extending an existing SubSet without invading semantic of theexisting SubSet. An ID that is not included in a SubSet may be added tothe ExtendedSubSet, and an existing contents attribute may be reused. Aspatial segment may be represented below. Semantics and XML syntax ofthe spatial segment may be represented as follows:

TileGroup id = 0 , contains = “15,16,21,22” DefaultView id = 1 ,contains = “11,12,17,18” ExtendedSubSet id = 0 , contains =“15,16,21,22” ExtendedSubSet id = 1 , contains = “11,12,17,18”<xs:complexType name=“ExtendedSubsetType”> <xs:complexContent><xs:extension base=“SubsetType”> <xs:attribute name=“id” type=“ID”use=“optional” /> </xs:extension> </xs:complexContent> </xs:complexType>

FIG. 4 is a diagram illustrating another example of a hierarchy of aspatial segment according to an embodiment.

According to an embodiment, an index of each spatial segment may beassigned. In other words, a current spatial segment description methodmay have only ID information. However, the ID information may merelyindicate each spatial segment, and may not be suitable for transmissionof additional information of each spatial segment. For example, whenseparate additional information is not provided, priority informationand the like may not be displayed because only position information ofeach spatial segment may be provided. Accordingly, there is a desire fora method of transferring separate additional information, for examplepriority information of spatial segments, information of the samesubset, and the like. ID information of each spatial segment, and anindex attribute may be independently transferred, and a receptionterminal may interpret index information based on a preset method. In anexample, in a Moving Picture Experts Group (MPEG)-DASH, to transferseparate additional information of each spatial segment, an indexattribute may be added to each spatial segment information. A meaning ofthe index and a method of using the index may be set in advance betweenan author and a terminal. The meaning of the index may be used aspriority information, and the same index may be used as a subset.Semantics and XML syntax of the spatial segment may be represented asfollows:

$\quad\begin{matrix}{{{Role}\mspace{14mu} {tileId}} = {{{\,^{``}{ts}}\; 1^{''}\mspace{14mu} {index}} = {{}_{}^{}{}_{}^{}}}} \\{{{Role}\mspace{14mu} {tileId}} = {{{\,^{``}{ts}}\; 2^{''}\mspace{14mu} {index}} = {{}_{}^{}{}_{}^{}}}} \\\ldots \\{{{Role}\mspace{14mu} {tileId}} = {{{\,^{``}{ts}}\; 24^{''}\mspace{14mu} {index}} = {{}_{}^{}{}_{}^{}}}}\end{matrix}$

FIG. 5 is a block diagram illustrating an example of a configuration ofthe client 100 according to an embodiment.

A controller 510 may perform operations 130 and 140. For example, thecontroller 510 may process metadata of an interval, and may selectcontent suitable for the interval based on the processed metadata.

A transceiver 520 may perform operations 120, 140, and 150. For example,the transceiver 520 may receive metadata of an interval of content fromthe server 110, may send a request for content suitable for the intervalto the server 110, and may receive the content from the server 110.

FIG. 6 is a diagram illustrating another example of a configuration ofthe client 100 according to an embodiment.

The client 100 may include an access engine 610, and a media engine 620.

The access engine 610 may be a DASH access engine.

The access engine 610 may receive metadata (for example, an MPD) fromthe server 110.

The access engine 610 may form requests, and may issue the formedrequests to the server 110.

The access engine 610 may receive content (for example, segments orparts of the segments) from the server 110.

The access engine 610 may provide the content to the media engine 620.

An output of the access engine 610 may include media (or a part of themedia) of an MPEG container (for example, an International Organizationfor Standardization (ISO)/International Electrotechnical Commission(IEC) 14492-12 ISO base media file format, or an ISO/IEC 13818-2 MPEG-2Transport Stream (TS)). Additionally, the output of the access engine610 may include timing information used to map internal timing of themedia to a timeline of a media presentation.

The media engine 610 may play back the provided content. For example,the media engine 610 may output media using the media and the timinginformation that are output from the access engine 610.

The above-described embodiments of the present invention may be recordedin non-transitory computer-readable media including program instructionsto implement various operations embodied by a computer. The media mayalso include, alone or in combination with the program instructions,data files, data structures, and the like. The program instructionsrecorded on the media may be those specially designed and constructedfor the purposes of the embodiments, or they may be of the kindwell-known and available to those having skill in the computer softwarearts. Examples of non-transitory computer-readable media includemagnetic media such as hard disks, floppy disks, and magnetic tape;optical media such as CD ROM disks and DVDs; magneto-optical media suchas optical discs; and hardware devices that are specially configured tostore and perform program instructions, such as read-only memory (ROM),random access memory (RAM), flash memory, and the like. Examples ofprogram instructions include both machine code, such as produced by acompiler, and files containing higher level code that may be executed bythe computer using an interpreter. The described hardware devices may beconfigured to act as one or more software modules in order to performthe operations of the above-described embodiments of the presentinvention, or vice versa.

Although a few exemplary embodiments of the present invention have beenshown and described, the present invention is not limited to thedescribed exemplary embodiments. Instead, it would be appreciated bythose skilled in the art that changes may be made to these exemplaryembodiments without departing from the principles and spirit of theinvention, the scope of which is defined by the claims and theirequivalents.

What is claimed is:
 1. A method of providing a media content performedby a server, comprising: receive a request for a segment of the mediacontent based on a metadata, from a client; and transmitting the mediacontent to the client, wherein the metadata is a spatial relationshipdescription (SRD) to express spatial relationships between spatialobjects.
 2. The method of claim 1, wherein the spatial object isrepresented by an adaptation set.
 3. The method of claim 1, wherein thespatial relationship expresses video representing a spatial part offull-frame video.
 4. The method of claim 1, wherein the SRD includesSupplementalProperty and EssentialProperty which are used to providespatial relationship information associated to the spatial object. 5.The method of claim 1, wherein the SRD includes source_id related to IDfor a source of the media content.
 6. The method of claim 1, wherein theSRD includes an x-axis position and a y-axis position of the spatialobject related to 2D position.
 7. The method of claim 1, wherein the SRDincludes a width and a height of the spatial object related to 2D size.8. The method of claim 1, wherein All SRD shares a same source_id havethe same origin and axes orientations.
 9. A method of providing a mediacontent performed by a server, comprising: A method for providing amedia content performed by a client, comprising: transmitting a requestfor a segment of the media content based on a metadata, to a server; andreceiving the media content from the server, wherein the metadata is aspatial relationship description (SRD) to express spatial relationshipsbetween spatial objects.
 10. The method of claim 9, wherein the spatialobject is represented by an adaptation set.
 11. The method of claim 9,wherein the spatial relationship expresses video representing a spatialpart of full-frame video.
 12. The method of claim 9, wherein the SRDincludes SupplementalProperty and EssentialProperty which are used toprovide spatial relationship information associated to the spatialobject.
 13. The method of claim 9, wherein the SRD includes source_idrelated to ID for a source of the media content.
 14. The method of claim9, wherein the SRD includes an x-axis position and a y-axis position ofthe spatial object related to 2D position.
 15. The method of claim 9,wherein the SRD includes a width and a height of the spatial objectrelated to 2D size.
 16. The method of claim 9, wherein All SRD shares asame source_id have the same origin and axes orientations.